This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bug make mxnet frequently get segfault on my machine, after some debugging and code tracing I realized it happens in the following condition:
DeleteOperator
DeleteOperator
pushesThreadedOpr::Delete(threaded_opr);
into the threaded engine.ThreadedOpr::Delete(threaded_opr);
is not satisfied because operationA
is using a dependent variable ofThreadedOpr::Delete(threaded_opr);
, soThreadedOpr::Delete(threaded_opr)
waitsA
.A
finishes and callsThreadedEngine::OnComplete(A)
.A
as complete (these code).threaded_opr
points to is destroyed and the memory address may be occupied by other objects.threaded_opr->temporary
in this line, and get a non-zero garbage value, then executes ThreadedOpr::Delete(threaded_opr); and destroy an innocent objectthreaded_opr
points to. (Probably also athreaded_opr
because object pool being used)This patch fixes the issue.
cc original author @tqchen